-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add alternative auth mechanism for API usage #833
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LVGTM! Noen spørsmål:
- Burde vi som nevnt kanskje plassert den et annet sted enn under "Admin" som forsvinner snart først som sist, slik at ikke brukerne trenger å lære seg dette to ganger?
- Litt lett å misse at man kan gi integrasjonen et navn; burde man kanskje startet med den modalen der man skriver inn navn og beskrivelse når man trykker på "Legg til klient"?
- Tror vi burde hashe secretene som vi lagrer i databasen for sikkerhets skyld.
- Lenke til API-dokumentasjonen fra et sted på siden?
- Burde kanskje få på rate limiting som vi snakket om.
- Er c67350a rebaset eller noe inn her med en feil?
7bf6a6f
to
fc5b0af
Compare
f8a4999
to
bd8feaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Noen spørsmål om småtweaks.
const apiLimiter = rateLimit({ | ||
windowMs: 15 * 60 * 1000, // 15 minutes | ||
max: 100, // max 100 requests per window | ||
message: 'Too many requests, please try again later.', | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥳
bd8feaa
to
e9bfa45
Compare
e9bfa45
to
e180685
Compare
No description provided.